datatools | DataTools in Python

You can use pandas.concat() to concat a list of dataframe.

Updated Answer

You can programmatically update the script task by replacing the appropriate XML node in the the DTSX file

The node path depends on where the script task has been created within the SSIS package, in my case the node path was

/DTS:Executable/DTS:Executables/DTS:Executable/DTS:ObjectData/pipeline/components/component[@refId="Package\Data Flow Task\Script Component"]/properties

The @refId you will be looking for will start with Package \ Dataflow name \ Component name

This node will have sub nodes which contains the C# scripts as well as the binary that was built off this script

The property name "SourceCode" contains the C# scipts in an array called arrayElements, the array will have three sub nodes for each file, these subnodes are called arrayElement, first value is the relative path and name, second is file encoding and third is the file content

The property name "BinaryCode" contains the .dll that was build from the scripts, it also contains an arrayElement array with two entries, first the dll name and the second the base64 encoded dll binary

To get the data to populate these items you will need to create a template of the C# build directory, apply your changes, build the code and take the resulting files and replace them on their appropriate nodes

To create the template open the script via SSIS task,

1. Click on the project in solution explorer to and go file save VstaProject.sln
2. Go to the saved folder, you get the folder off the solutions properties dialog
3. Copy this folder somewhere so that you can reuse it to build your custom stuff
4. Modify the .cs files in your template directory and add your custom reference dll's to your .csproj file
5. Call MSBUILD in the same directory as your .csproj to output the dll, its important that you use the VS MSBUILD, VS2017 you can find it in

C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\15.0\Bin\msbuild.exe

1. Take these files and package them into a XML node in the DTSX file

Initial Answer

Microsoft provides a workaround for loading DLL's that aren't in the GAC

Load assembly that isnt in the GAC

Please see below extract from a SSIS script, I loaded the JSON dll's from the nuget install directory. This DLL is not in the GAC

The problem you have there is that CSS transitions are preventing you from clicking those elements. One possible solution would be disabling all CSS animations on the page.

You can add that after the goto call:

Even I was facing the same issue. Then I realized I had not added supported jars in the BIRT POJO Data Source. Along with the main POJO jar file, please add all the supporting libraries or jar files the classes in POJO jar refers to in the POJO Data Source. For example if the class needs GSON jar, add that jar file in the POJO Data Source.

Previous failed installations left VS2017 recognising that the installation was present in Visual Studio Installer. I removed the installation, restarted and the re-install was successful...

I fixed it. What was happening was that while this code was in the PCL code, the code that called it was in the platform-specific code. I created some interfaces and fired some events that got the PCL code to run this code, and it worked.

I don't know WHY it worked... but it worked.

After some research, I discovered that creating an IConnectionProfile actually uses java.sql.DriverManager under the covers. If I set DriverManager.setLoginTimeout before creating the connection profile, the timeout is recognized.

However, I also learned that setLoginTimeout is not guaranteed to be recognized by all drivers. For instance, Informix, Netezza, and PostgreSQL did not use the time set by setLoginTimeout. For my use case, those databases did not apply, so I just used setLoginTimeout.

While I didn't use it for my solution, it is possible to use properties to set the login timeout (see original post). However, the property name and value type (seconds or milliseconds) are driver dependent.

Following are the results for individual databases I tested.

Here are the results of my tests using using setLoginTimeout with a low value (2 seconds) and a URL guaranteed to timeout:

• DB2 UDB - works
• DB2 zOS - works
• HIVE - works
• INFORMIX - does not work - uses its own timeout (20+ seconds)
• NETEZZA - does not work - uses its own timeout (20+ seconds)
• ORACLE - works (about 2-3 seconds slow)
• POSTGRES - does not work - uses its own timeout 10+ sec
• SQL_SERVER - works
• SYBASE - works
• TERADATA - works

Here are the test results using properties (the property name and value type are in parentheses):

• DB2 UDB (loginTimeout, seconds) - works
• DB2 zOS (loginTimeout, seconds) - works
• HIVE (loginTimeout, seconds) - works
• INFORMIX (INFORMIXCONTIME, seconds) - works
• ORACLE (oracle.net.CONNECT_TIMEOUT, milliseconds) - works (about 2-3 seconds slow)
• POSTGRES - no property found
• NETEZZA (loginTimeout, seconds) - works if the property is in the URL instead of a separate property.
• SQL_SERVER (loginTimeout, seconds) - works
• SYBASE - no property found
• TERADATA - no property found

I have finally found the mistake...

I had to load first

• Microsoft.SharePoint.Client.Runtime.dll

And afterwards i had to load the other library

• Microsoft.SharePoint.Client.dll

So in Main I switched the library-loading:

You cannot generate an installable binary -i.e. Android .apk nor iOS .ipa- using Visualizer Starter. Visualizer Starter is meant as a prototyping tool only, used for quick ideation and for UX designers.

In order to build a .apk file you'll need to install Visualizer Enterprise. All downloads are available from the Kony release site here. You'll have to register for a Kony developer account in order to download, but this is free of charge.

Once you have installed Visualizer Enterprise, you'll be able to build the .apk from the Visualizer UI or from the command line.